home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000186_misckit-reques…aska.et.byu.edu_Wed Apr 27 01:10:33 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
2KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00321; Wed, 27 Apr 94 01:10:23 -0600
Received: from darth.byu.edu by alaska.et.byu.edu; Wed, 27 Apr 1994 01:07:04 -0600
Received: by darth.byu.edu (NX5.67d/NX3.0M)
id AA00315; Wed, 27 Apr 94 01:08:07 -0600
Date: Wed, 27 Apr 94 01:08:07 -0600
From: Don Yacktman <don@darth.byu.edu>
Message-Id: <9404270708.AA00315@darth.byu.edu>
Received: by NeXT.Mailer (1.100.RR)
Received: by NeXT Mailer (1.100.RR)
To: misckit@alaska.et.byu.edu
Subject: Re: MIME Text Object?
Reply-To: don@darth.byu.edu
Well, on the topic of mail messages and such... this kind of
came up a while back and the suggestion was to do a generic
"message" type of class, and then subclasses for the various
types of messages you might send...ASCII E-Mail, NeXTMail,
MIME, Usenet News postings, etc., each with an appropriate
"deliver" method. I still think that's potentially a good idea.
In fact, besides the DolphinKit, I am working on objects
which encapsulate ASCII and NeXTMail messages. I will let
someone else make the MIME version, I think, mostly due to
time constraints. They will appear in the MiscKit as soon as
they are stable. I _have_ got them "basically" working, but
need to refine a few things in the design and make it a bit
more flexible. But I can send full blown NeXTMail with
attachments and everything already... I would think that
generating MIME-based messages shouldn't be too terribly hard
to do once the interface is solid. (Still, it's more work
than NeXTMail since the formatting requires a translation
from rtf to MIME.) To my knowledge, though, no one is doing
anything with MIME as a free object. By the way, this handles
packing up and sending. The converse--using these objects to
unpack the message and stuff it into a Text object seems more
like what the original question was asking. It seems like the
same "message" object, designed right, ought to be able to do
both...right? :-) Anyway, my work is cut out for me on
several fronts right now...
If someone needs to look at my objects in their current
messy, alpha state, let me know and you can have a peek.
---
Later,
-Don Yacktman
Don_Yacktman@byu.edu